chore: release workflow + distribution/adoption doc#2
Conversation
release.yml builds sdist+wheel and publishes a GitHub Release on v* tags. docs/distribution.md lays out how loops adopt agent-core as a real (always-on) dependency: uv git source pin (recommended), Release wheel, hosted index, or making the repo public; with the per-loop reversible path and the CI-auth tradeoff. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 87ad4f4ab4
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ### B. GitHub Release wheel + `--find-links` | ||
| Install the published wheel directly: | ||
| ``` | ||
| uv pip install --find-links https://github.com/AS215932/agent-core/releases/download/v0.1.0 agent-core |
There was a problem hiding this comment.
For option B, this is the GitHub release download prefix rather than an HTML page with archive links or a direct wheel URL. I checked pip install --help, which says --find-links parses a URL/HTML for links to archives or scans a local directory, so uv pip install will not discover agent_core-0.1.0-py3-none-any.whl at this path when a loop follows the documented Release-wheel install path; it will fail or fall back to an index package. Use the concrete asset URL or a release page that actually links to the wheel.
Useful? React with 👍 / 👎.
1 participant
Adds the publishing mechanism for
agent-coreand documents how loops can adopt it as areal (always-on) dependency.
.github/workflows/release.yml— onv*tags, builds sdist+wheel (uv build) andpublishes a GitHub Release with the artifacts.
docs/distribution.md— adoption options (uv git source pin / Release wheel / hostedprivate index / make public) with a recommendation and the CI-auth tradeoff.
After merge, tagging
v0.1.0produces the first released artifact. Loops stay on optionalemission until a distribution choice is made (per-loop, reversible).
🤖 Generated with Claude Code